<html>

<head>
	<title>Test SVN live</title>
</head>
<body>
	<article>
		<header>
			<h1>Test SVN live in Telerik Academy</h1>
		</header>
		<p>
			Apache Subversion (often abbreviated SVN, after the command name svn) is a software versioning and revision control
			system distributed under an open source license. Developers use Subversion to maintain current and historical
			versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor
			to the widely used Concurrent Versions System (CVS).
		</p>
		<p>
			The Subversion filesystem uses transactions to keep changes atomic. A transaction operates on a specified revision of 
			the filesystem, not necessarily the latest. The transaction has its own root, on which changes are made. It is then 
			either committed and becomes the latest revision, or is aborted. The transaction is actually a long-lived filesystem 
			object; a client does not need to commit or abort a transaction itself, rather it can also begin a transaction, exit, 
			and then can re-open the transaction and continue using it. Multiple clients can access the same transaction and work 
			together on an atomic change, though no existing clients expose this capability.
		</p>
		<p>
				Is Subversion the right tool? "If you need to archive old versions of files and directories, 
				possibly resurrect them, or examine logs of how they've changed over time, then Subversion is exactly the right tool for you.
				" So write the authors of O'Reilly's Version Control with Subversion, 2nd Ed.--C. Michael Pilato, Ben Collins-Sussman, 
				and Brian Fitzpatrick. And here, these members of the Subversion development team give you their top tips for avoiding the pesky network round-trip, 
				safely moving files and directories with wild 
				abandon, teaching your Subversion client to 
				add certain properties to your files automatically, and more. Check them out.
		</p>
	</article>
</body>
</html>